Release 10.1A: OpenEdge Development:
Progress Dynamics Web Development Guide


Context management

Since the Web server does not maintain context between Web requests, you must implement storing and retrieving context information in your 4GL code.

To store context information on the server between Web requests, use the setPropertyList function in the Session Manager API. This function has the following input parameters:

The following example shows the usage:

DYNAMIC-FUNCTION("setPropertyList":U IN gshSessionManager, pcSDOName, 
pcSDOInfo, NO). 

To retrieve context information on the server between Web requests, use the getPropertyList function in the Session Manager API. The function returns a CHR(3)-delimited list of property values. This function has the following input parameters:

The following example shows the usage:

DYNAMIC-FUNCTION("getPropertyList":U IN gshSessionManager, pcSDOName, NO). 

To store temporary context information on the server only for the duration of the Web request, use the setProperty function in the Web Request Manager API.

To add to a list of temporary context information on the server only for the duration of the Web request, use the addProperty function in the Web Request Manager API. This function is useful for accumulating lists of UI changes that are sent to the client at the end of a Web request.

To retrieve temporary context information on the server that has been stored using the setProperty function, use the getProperty function in the Web Request Manager API.

For more information on these functions, see OpenEdge Development: Progress Dynamics Managers API Reference .


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095